core: Fix thread section alignment. #209
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
iabdalkader
force-pushed
the
fix_thread_section_alignment
branch
from
6588cbd to
ccc56ce
Compare
iabdalkader
changed the title
iabdalkader
force-pushed
the
fix_thread_section_alignment
branch
2 times, most recently
from
8bdc53e to
1bab673
Compare
The _static_thread_data struct contains int64_t members that require 8-byte alignment. When placed in a 4-byte aligned section, it causes the linker to insert padding, which in turn causes __static_thread_data_list_start to point to the padding not to the first iterable. GNU ld automatically aligns output sections based on the strictest alignment requirement of input sections, so moving __static_thread_data_list to its own section fixes the problem. Signed-off-by: iabdalkader <[email protected]>
According to Zephyr documentation, k_thread_create() both initializes and starts the thread. The second loop that was calling k_thread_start() on each static thread was redundant. Signed-off-by: iabdalkader <[email protected]>
iabdalkader
force-pushed
the
fix_thread_section_alignment
branch
from
1bab673 to
9416d15
Compare
pillo79
reviewed
Oct 15, 2025
|
|
||
| .static_thread_data_area : { | ||
| __static_thread_data_list_start = .; | ||
| KEEP(*(SORT_BY_NAME(.__static_thread_data.static.*))); |
There was a problem hiding this comment.
Suggested change
| KEEP(*(SORT_BY_NAME(.__static_thread_data.static.*))); | |
| KEEP(*(.static_thread_data_area SORT_BY_NAME(.__static_thread_data.*))); |
|
|
||
| .static_thread_data_area : { | ||
| __static_thread_data_list_start = .; | ||
| KEEP(*(SORT_BY_NAME(.__static_thread_data.static.*))); |
There was a problem hiding this comment.
Suggested change
| KEEP(*(SORT_BY_NAME(.__static_thread_data.static.*))); | |
| KEEP(*(.static_thread_data_area SORT_BY_NAME(.__static_thread_data.*))); |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The _static_thread_data struct contains int64_t members that require 8-byte alignment. When placed in a 4-byte aligned section, it causes the linker to insert padding, which in turn causes
__static_thread_data_list_startto point to the padding not to the first iterable.GNU ld automatically aligns output sections based on the strictest alignment requirement of input sections, so moving
__static_thread_data_listto its own section fixes the problem.